-
Notifications
You must be signed in to change notification settings - Fork 451
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change for 7702 for devnet-4 #7590
Conversation
private bool ValidateAuthoritySignature(Signature signature) | ||
{ | ||
UInt256 sValue = new(signature.SAsSpan, isBigEndian: true); | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this not needed anymore?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It went from invalidating the tx to just invalidating the tuple instead, so the check is now in TransactionProcessor
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
New spec for 7702 here:
https://eips.ethereum.org/EIPS/eip-7702
Changes
assert auth.chain_id < 2 **64
assert auth.nonce < 2 **64
assert len(auth.address) == 20
assert auth.y_parity < 2 **8
assert auth.r < 2 **256
assert auth.s < 2 **256
Tuple fields have been bounded by their type during RLP serialization/deserialization, so any field exceeding the bounds will result in
RlpException
What types of changes does your code introduce?